examples/sleep: clarify /proc vs procfs wording #333
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Use "/proc" when the comment refers to the actual file (/proc/sleep) and keep "proc" when it denotes the procfs mechanism or related helper APIs. This makes the documentation consistent and avoids ambiguity between a file path and the proc filesystem itself. Signed-off-by: Chia-Hao Chiu <[email protected]>
|
LGTM! |
|
Thank @Jordymalone for contributing! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Use "/proc" when the comment refers to the actual file (/proc/sleep) and keep "proc" when it denotes the procfs mechanism or related helper APIs. This makes the documentation consistent and avoids ambiguity between a file path and the proc filesystem itself.
Summary by Bito
This pull request enhances the clarity of comments in 'examples/sleep.c' by ensuring consistent references to the file path '/proc' and the procfs mechanism. This improves documentation quality and reduces ambiguity.